System and method for configuring a client electronic device

ABSTRACT

A method and computer program product for obtaining a main configuration file from a client electronic device upon the client electronic device being coupled to at least a portion of a media distribution system. The main configuration file defines one or more enhanced functionalities of the client electronic device. The client electronic device is coupled to the at least a portion of the media distribution system using a binary transfer protocol configured to transfer media data from the at least a portion of a media distribution system to a client electronic device.

RELATED APPLICATION(S)

This application claims the benefit of the following applications, eachof which is herein incorporated by reference: U.S. Provisional PatentApplication Ser. No. 60/842,056, entitled “API-ACCESSIBLE MEDIADISTRIBUTION SYSTEM” and filed 31 Aug. 2006; U.S. Provisional PatentApplication Ser. No. 60/843,212, entitled “API-ACCESSIBLE MEDIADISTRIBUTION SYSTEM” and filed 8 Sep. 2006; and U.S. Provisional PatentApplication Ser. No. 60/941,526, entitled “PERSONAL MEDIA DEVICECONFIGURATION SYSTEM AND METHOD” and filed 1 Jun. 2007.

TECHNICAL FIELD

This disclosure relates to client electronic devices and, moreparticularly, to the configuring of client electronic devices.

BACKGROUND

Media distribution systems (e.g., the Rhapsody™ service offered byRealNetworks, Inc. of Seattle, Wash.) distribute media data to a user'sclient electronic device (e.g., a personal media device, a personaldigital assistant, or a multimedia cellular telephone) from a mediaserver. A media distribution system may distribute media data byallowing a user to e.g., receive downloaded media data files and/orstream remote media data files.

Typically, different media distribution systems offer different levelsof functionality and different features. For example, one mediadistribution system may offer “radio channels” while another mediadistribution system may not. Often, in order to take advantage of suchenhanced functionality, a custom (i.e., nonstandard) communicationsprotocol may be required for the client electronic device to communicatewith the media distribution system. Unfortunately, by requiring theclient electronic device to communicate using a custom communicationprotocol, manufacturers may be reluctant to adapt their devices to workwith such a custom communications protocol.

SUMMARY OF DISCLOSURE

In a first implementation, a method includes obtaining a mainconfiguration file from a client electronic device upon the clientelectronic device being coupled to at least a portion of a mediadistribution system. The main configuration file defines one or moreenhanced functionalities of the client electronic device. The clientelectronic device is coupled to the at least a portion of the mediadistribution system using a binary transfer protocol configured totransfer media data from the at least a portion of a media distributionsystem to a client electronic device.

One or more of the following features may be included. One or moresupplemental configuration files may be provided to the clientelectronic device. The one or more supplemental configuration files maybe chosen from the group consisting of: a subscription file; a messagingfile; a channels file; an add to library file; a ratings file; a ratingsmapping file; and a radio PC file. At least one of the mainconfiguration file and the one or more supplemental configuration filesmay be an XML configuration file.

The client electronic device may be a MTP-enabled client electronicdevice. The MTP-enabled client electronic device may be a PlaysForSureclient electronic device.

The at least a portion of the media distribution system may include aclient-side media manager. The client-side media manager may beconfigured to interface with a server-side media distribution system.The at least a portion of the media distribution system may include aserver-side media distribution system.

The client electronic device may be configured to be wirelessly-coupledto the at least a portion of the media distribution system. The clientelectronic device may be configured to be hardwire-coupled to the atleast a portion of the media distribution system.

A SyncID, transferable using the binary transfer protocol, may beprocessed to extract one or more of a versionid, a trackid, an artistid,an albumid, an albumartistid, and a genreid. One or more of theversionid, the trackid, the artistid, the albumid, the albumartistid andthe genreid may be stored within a device database included within theclient electronic device.

In another implementation, a computer program product resides on acomputer readable medium that has a plurality of instructions stored onit. When executed by a processor, the instructions cause the processorto perform operations including obtaining a main configuration file froma client electronic device upon the client electronic device beingcoupled to at least a portion of a media distribution system. The mainconfiguration file defines one or more enhanced functionalities of theclient electronic device. The client electronic device is coupled to theat least a portion of the media distribution system using a binarytransfer protocol configured to transfer media data from the at least aportion of a media distribution system to a client electronic device.

One or more of the following features may be included. One or moresupplemental configuration files may be provided to the clientelectronic device. The one or more supplemental configuration files maybe chosen from the group consisting of: a subscription file; a messagingfile; a channels file; an add to library file; a ratings file; a ratingsmapping file; and a radio PC file. At least one of the mainconfiguration file and the one or more supplemental configuration filesmay be an XML configuration file.

The client electronic device may be a MTP-enabled client electronicdevice. The MTP-enabled client electronic device may be a PlaysForSureclient electronic device.

The at least a portion of the media distribution system may include aclient-side media manager. The client-side media manager may beconfigured to interface with a server-side media distribution system.The at least a portion of the media distribution system may include aserver-side media distribution system.

The client electronic device may be configured to be wirelessly-coupledto the at least a portion of the media distribution system. The clientelectronic device may be configured to be hardwire-coupled to the atleast a portion of the media distribution system.

A SyncID, transferable using the binary transfer protocol, may beprocessed to extract one or more of a versionid, a trackid, an artistid,an albumid, an albumartistid, and a genreid. One or more of theversionid, the trackid, the artistid, the albumid, the albumartistid andthe genreid may be stored within a device database included within theclient electronic device.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will become apparent from the description, the drawings, andthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of a media distribution system, aclient-side media manager, and a client electronic device coupled to adistributed computing network;

FIG. 2 is an isometric view of the client electronic device of FIG. 1;

FIG. 3 is a diagrammatic view of the client electronic device of FIG. 1;and

FIG. 4 is a flowchart of a process executed by the media distributionsystem of FIG. 1.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE DISCLOSURE System Overview:

Referring to FIG. 1, there is shown a server-side configuration process10 and a client-side configuration process 12. As will be discussedbelow in greater detail, each of server-side configuration process 10and client-side configuration process 12 may configure a clientelectronic device to interface with and obtain media data 14 from mediadistribution system 16.

Examples of media data 14 may include, but are not limited to,digitally-encoded audio and/or video media data that may be compressedusing known compression techniques. Examples of such compressiontechniques may include but are not limited to MPEG-1, MPEG-2, MPEG-4,H.263, H.264, Advanced Audio Coding, and other techniques promulgated bye.g., the International Standards Organization and the Motion PictureExperts Group.

Media data 14 may include but is not limited to: purchased downloadsreceived from media distribution system 16 (i.e., media data licensed toa user for use in perpetuity); subscription downloads received frommedia distribution system 16 (i.e., media data licensed to a user foruse while a valid subscription exists with media distribution system16); and media data streamed from media distribution system 16, forexample.

Media distribution system 16 may provide media data (i.e., in the formof streams and/or files) to a plurality of users (e.g., users 18, 20,22, 24). Examples of media distribution system 16 may include but arenot limited to the Rhapsody™ service offered by RealNetworks, Inc. ofSeattle, Wash.

Media distribution system 16 may be a server application that resides onand is executed by server computer 26 (e.g., a server computer) that isconnected to network 28 (e.g., the Internet). Server computer 26 may bea web server running a network operating system, examples of which mayinclude but are not limited to Microsoft Windows XP Server™, NovellNetware™, or Redhat Linux™. Examples of server computer 26 may includebut are not limited to: a personal computer, a server computer, and aplurality of server computers.

Server computer 26 may also execute a web server application, examplesof which may include but are not limited to Microsoft IIS™, NovellWebserver™, or Apache Webserver™, that allows for HTTP (i.e., HyperTextTransfer Protocol) access to server computer 26 via network 28. Network28 may be connected to one or more secondary networks (e.g., network30), such as: a local area network; a wide area network; or an intranet,for example.

The instruction sets and subroutines of media distribution system 16 andserver-side configuration process 10, which may be stored on storagedevice 32 coupled to server computer 26, may be executed by one or moreprocessors (not shown) and one or more memory architectures (not shown)incorporated into server computer 26. Additionally, media data 14available from media distribution system 16 may be stored on e.g.,storage device 32 coupled to server computer 26. Storage device 32 mayinclude but is not limited to a hard disk drive, a tape drive, anoptical drive, a RAID array, a random access memory (RAM), or aread-only memory (ROM).

Users 18, 20, 22, 24 may access media distribution system 16 throughe.g., network 28 and/or secondary network 30. Further, server computer26 (i.e., the computer that executes media distribution system 16) maybe connected to network 28 through secondary network 32, as illustratedwith phantom link line 34.

Media distribution system 16 may be accessed through various clientelectronic devices, examples of which may include, but are not limitedto: personal media device 36; personal media device 38, personal digitalassistant 40; data-enabled cellular telephone 42; televisions (notshown); cable boxes (not shown); Internet radios (not shown); ordedicated network devices (e.g., A Roku™ Soundbridge M500, M1000 andM2000; not shown), for example.

Media distribution system 16 may be accessed directly or may be accessedindirectly (e.g., through a client computer) by the client electronicdevices (e.g., personal media device 36; personal media device 38,personal digital assistant 40; data-enabled cellular telephone 42). Forexample, users 18, 22, 24 are shown directly accessing mediadistribution system 16 through personal media device 36, personaldigital assistant 40, and data-enabled cellular telephone 42.Conversely, user 20 is shown indirectly accessing media distributionsystem 16 through personal media device 38 via client computer 44.

The client electronic devices may be wirelessly-coupled or hardwired tonetwork 30, 32 (and, therefore, media distribution system 16).

For example, personal media device 38 is shown hardwired to clientcomputer 44, which is shown directly coupled to network 28 via ahardwired network connection. Client computer 44 may execute aclient-side media manager 46 (examples of which may include but are notlimited to Microsoft Internet Explorer™ available from Microsoft Inc, ofRedmond, Wash., Rhapsody™ client & RealPlayer™ client available fromRealNetworks, Inc. of Seattle, Wash., and a specialized interface) thatallows e.g., user 20 to access and configure media distribution system16 via network 28 (or network 30). Client computer 44 may execute anoperating system, examples of which may include but are not limited toMicrosoft Windows XP™ and Redhat Linux™.

The instruction sets and subroutines of client-side media manager 46,which may be stored on a storage device 48 coupled to client computer44, may be executed by one or more processors (not shown) and one ormore memory architectures (not shown) incorporated into client computer44. Storage device 48 may include but is not limited to a hard diskdrive, a tape drive, an optical drive, a RAID array, a random accessmemory (RAM), or a read-only memory (ROM).

As discussed above, the client electronic devices may bewirelessly-coupled to network 30, 32 (and, therefore, media distributionsystem 16). For example, personal media device 36 is shown wirelesslycoupled to network 28 via a wireless communication channel 50established between personal media device 36 and wireless access point(i.e., WAP) 52, which is shown directly coupled to network 28. WAP 52may be, for example, an IEEE 802.11a, 802.11b, 802.11g, Wi-Fi, and/orBluetooth device that is capable of establishing communication channel50 between personal media device 36 and WAP 52.

As is known in the art, the IEEE 802.11x specifications may use Ethernetprotocol and carrier sense multiple access with collision avoidance(i.e., CSMA/CA) for path sharing. The various 802.11x specifications mayuse phase-shift keying (i.e., PSK) modulation or complementary codekeying (i.e., CCK) modulation, for example. As is known in the art,Bluetooth is a telecommunications industry specification that allowse.g., mobile phones, computers, and personal digital assistants to beinterconnected using a short-range wireless connection.

Additionally, personal digital assistant 40 is shown wirelessly coupledto network 28 via cellular/network bridge 54 (which is shown directlycoupled to network 28); and data-enabled cellular telephone 42 is shownwirelessly coupled to network 30 via cellular/network bridge 56 (whichis shown directly coupled to network 30).

Client Electronic Devices:

As discussed above, examples of client electronic devices may includepersonal media devices 36, 38, personal digital assistant 40, anddata-enabled cellular telephone 42. Accordingly, while the followingdisclosure is directed towards personal media device 38, it isunderstood that the following disclosure may be equally applied to anyclient electronic device (including personal media device 36, personaldigital assistant 40, cellular telephone 42, televisions (not shown);cable boxes (not shown); internet radios (not shown); and dedicatednetwork devices (not shown).

Referring also to FIG. 2, personal media device 38 may be connected toe.g., client computer 44 via a docking cradle 100. Typically, personalmedia device 38 includes a bus interface (to be discussed below ingreater detail) that couples personal media device 38 to docking cradle100. Docking cradle 100 may be coupled (with cable 102) to e.g., aUniversal Serial Bus (i.e., USB) port, a serial port, or an IEEE 1394(i.e., FireWire) port included within client computer 44. For example,the bus interface included within personal media device 38 may be a USBinterface, and docking cradle 100 may function as a USB hub (i.e., aplug-and-play interface that allows for “hot” coupling and uncoupling ofpersonal media device 38 and docking cradle 100).

Client computer 44 may function as an Internet gateway for personalmedia device 38. For example, through the use of e.g., the universalplug and play protocol (i.e., UPnP), personal media device 38 may useclient computer 44 to access media distribution system 16 via network 28(and network 30) and obtain media data 14. Specifically, upon receivinga request for media distribution system 16 from personal media device38, client computer 44 (acting as an internet client on behalf ofpersonal media device 38), may request the appropriate web page/servicefrom server computer 26 (i.e., the computer that executes mediadistribution system 16). When the requested web page/service is returnedto client computer 44, client computer 44 may relate the returned webpage/service to the original request (placed by personal media device38) and may forward the web page/service to personal media device 38.Accordingly, client computer 44 may function as a conduit for couplingpersonal media device 38 to server computer 26 and, therefore, mediadistribution system 16.

Referring also to FIG. 3, a diagrammatic view of personal media device38 is shown. Personal media device 38 may include microprocessor 150(e.g., an ARM™ microprocessor produced by Intel Corporation of SantaClara, Calif.), non-volatile memory (e.g., read-only memory 152), andvolatile memory (e.g., random access memory 154); each of which may beinterconnected via one or more data/system buses 156, 158. Personalmedia device 38 may also include an audio subsystem 160 for providinge.g., an analog audio signal to an audio jack 162 for removably engaginge.g., a headphone assembly 164, a remote speaker assembly 166, or an earbud assembly 168, for example. Alternatively, personal media device 38may be configured to include one or more internal audio speakers (notshown).

Personal media device 38 may execute a device application 58 (examplesof which may include but are not limited to Rhapsody™ client,RealPlayer™ client, or a specialized interface). Personal media device38 may run an operating system, examples of which may include but arenot limited to Microsoft Windows CE™, Redhat Linux™, Palm OS™, or adevice-specific (i.e., custom) operating system.

The instruction sets and subroutines of device application 58, which maybe stored on storage device 60 coupled to personal media device 38, maybe executed by one or more processors (not shown) and one or more memoryarchitectures (not shown) incorporated into personal media device 38.Storage device 60 may be, for example, a hard disk drive, an opticaldrive, a random access memory (RAM), a read-only memory (ROM), a CF(i.e., compact flash) card, an SD (i.e., secure digital) card, aSmartMedia card, a Memory Stick, and a MultiMedia card, for example.

Personal media device 38 may also include user interface 170 and displaysubsystem 172. User interface 170 may receive data signals from variousinput devices included within personal media device 38, examples ofwhich may include (but are not limited to): backward skip switch 104;forward skip switch 106; play/pause switch 108; menu switch 110;selector switch 112; and wheel assembly 114, for example. Displaysubsystem 172 may provide display signals to display panel 116 includedwithin personal media device 38. Display panel 116 may be an activematrix liquid crystal display panel, a passive matrix liquid crystaldisplay panel, or a light emitting diode display panel, for example.

Audio subsystem 160, user interface 170, and display subsystem 172 mayeach be coupled with microprocessor 150 via one or more data/systembuses 174, 176, 178 (respectively).

As discussed above, personal media device 38 may include bus interface180 for interfacing with e.g., client computer 44 via docking cradle100. Additionally and as discussed above, personal media device 38 maybe wirelessly coupled to network 28 (and/or other personal mediadevices) via e.g., a wireless communication channel 50 establishedbetween personal media device 38 and e.g., WAP 52. Accordingly, personalmedia device 38 may include a wireless interface 182 forwirelessly-coupling personal media device 38 to network 28 (or network30) and/or other personal media devices. Wireless interface 182 may becoupled to an antenna assembly 184 for RF communication to e.g., WAP 52,and/or an IR (i.e., infrared) communication assembly 186 for infraredcommunication with e.g., a second personal media device. Further and asdiscussed above, personal media device 38 may include a storage device60 for storing the instruction sets and subroutines of deviceapplication 58. Additionally, storage device 60 may be used to storemedia data (e.g., files and/or streams) downloaded from mediadistribution system 16.

Storage device 60, bus interface 180, and wireless interface 182 mayeach be coupled with microprocessor 150 via one or more data/systembuses 188, 190, 192 (respectively). As discussed above, mediadistribution system 16 may distribute media data to users 18, 20, 22, 24such that the media data distributed may be in the form of media datastreams and/or media data files.

Configuration Process:

As discussed above, each of server-side configuration process 10 andclient-side configuration process 12 may configure a client electronicdevice (e.g., personal media device 38) to interface with and obtainmedia data 14 from media distribution system 16.

Typically, when the client electronic device is communicating with mediadistribution system 16 through another device, a client-sideconfiguration process may be executed on the device through which theclient electronic device is connecting. For example, as personal mediadevice 38 communicates with media distribution system 16 though clientcomputer 44, client-side configuration process 12 may be executed onclient computer 44 and may configure personal media device 38 tointerface with media distribution system 16.

Alternatively, when the client electronic device is directlycommunicating with media distribution system 16, a server-sideconfiguration process may be executed on the device on which mediadistribution system 16 is executed. For example, as personal mediadevice 36, personal digital assistant 40, and data-enabled cellulartelephone 42 directly communicate with media distribution system 16,server-side configuration process 10 may be executed on server computer26 and may configure personal media device 36, personal digitalassistant 40, and data-enabled cellular telephone 42 to interface withmedia distribution system 16.

When the client electronic devices (e.g., personal media devices 36, 38,personal digital assistant 40 and data-enabled cellular telephone 42)communicate with media distribution system 16 (either directly orthrough client computer 44), a binary transfer protocol may be utilizedto e.g., configure the client electronic device and transfer media datafiles to the client electronic device from e.g., media distributionsystem 16 or client-side media manager 46. Examples of the binarytransfer protocol may include but are not limited to a Media TransferProtocol (i.e., MTP). Accordingly, the client electronic devices (e.g.,personal media devices 36, 38, personal digital assistant 40 anddata-enabled cellular telephone 42) may be MTP-enabled client electronicdevices.

MTP is a set of custom extensions of the Picture Transfer Protocol (PTP)devised by Microsoft™. While PTP was configured to allow for thetransfer of digital images from digital cameras to personal computers,MTP allows for the transfer of media data from various client electronicdevices (e.g., personal media devices 36, 38, personal digital assistant40 and data-enabled cellular telephone 42) to personal computers.

Examples of such MTP-enabled client electronic devices may include butare not limited to a PlaysForSure client electronic device.

Microsoft™ PlaysForSure is a certification given by Microsoft™ toportable devices (e.g., personal media devices 36, 38, personal digitalassistants 40, data-enabled cellular telephone 42) and content services(e.g., media distribution system 16) that have been tested forcompatibility and performance requirements (e.g., CODEC support, DRMsupport, user interface responsiveness, device performance,compatibility with Windows Media Player™, and synchronizationperformance)

Configuration File

Upon the client electronic device directly or indirectly accessing mediadistribution system 16, server-side configuration process 10 orclient-side configuration process 12 (respectively) may obtain 200 mainconfiguration file 62 from the client electronic device. Mainconfiguration file 62 may be stored within a known directory withine.g., storage device 60 of e.g., personal media device 38. As discussedabove, examples of client electronic devices may include personal mediadevices 36, 38, personal digital assistant 40, and data-enabled cellulartelephone 42. Accordingly, while the above disclosure and the followingdisclosure is directed towards personal media device 38, it isunderstood that the following disclosure may be equally applied to anyclient electronic device (including personal media device 36, personaldigital assistant 40, cellular telephone 42, televisions (not shown);cable boxes (not shown); internet radios (not shown); and dedicatednetwork devices (not shown).

Main configuration file 62 may be an XML configuration file that isinstalled at the time that the device is manufactured and may define oneor more enhanced functionalities of personal media device 38. An exampleof main configuration file 62 is as follows:

<?xml version=“1.0” encoding=“UTF-8”?> <xsl:stylesheetxmlns:xsl=“http://www.w3.org/TR/WD-xsl”>  <xsl:template>  <!--Capabilities Block (ReadOnly)-->   <Capabilities>    <!--RhapsodyDNA version (starts at 100)-->    <RhapDNAVersion/>    <!--Boolean, doesthis device support channels?-->    <RhapChannelCapable />   <!--Preferred Album Art Size/-->    <PreferredAlbumArtSize/>   <!--Path to Video files-->     <VideoPath/>     <!--Path to PhotoFiles-->     <PhotoPath/>     <!--Path to Audio(Music) files-->    <AudioPath/>     <!--Path to Rhapsody Artist Information Files-->    <ArtistInfoPath/>     <!--Path to Rhapsody Text Files-->    <TextPath/>     <!--Path to Recorded audio files-->    <RecordingsPath/>    <!-Path to Channel files→    <ChannelsPath> <!--Determines whether devices can display a service specific splash screen on device start-->    <SupportsServiceLogo/>   </Capabilities> </xsl:template> </xsl:stylesheet>

For illustrative purposes, main configuration file 62 is shown to defineone or more of the following functionalities, examples of which mayinclude but are not limited to:

-   -   A version indicator that indicates to media distribution system        16 and/or client-side media manager 46 what version of the        extensions specification is being implemented on personal media        device 38.    -   A Boolean value indicating whether personal media device 38        supports channels. As is known in the art, channels are similar        to radio stations (or constantly refreshed playlists) on        personal media device 38, which automatically update with new        media content that replaces the media content that the user        already listened to. This automatic updating process may occur        each time that personal media device 38 is coupled with media        distribution system 16 and/or client-side media manager 46.    -   An integer value may represent the preferred album art size for        personal media device 38.    -   A series of path attributes may define the preferred location on        personal media device 38 for various types of media.    -   A Boolean value may indicate whether personal media device 38        supports displaying a service logo splash screen at personal        media device 38 start up.

Once configuration process 10, 12 obtains 200 main configuration file 62from personal media device 38, configuration process 10, 12 may process202 main configuration file 62 so that media distribution system 16and/or client-side media manager 46 may determine whichfeatures/functionality are supported by personal media device 38.

Once main configuration file 62 is processed 202, configuration process10, 12 may provide 204 one or more supplemental configuration files 64to the client electronic device (e.g., personal media device 38), whichmay further define the functionality of the client electronic device.One or more of the supplemental configuration files 64 may be an XMLconfiguration file.

Examples of supplemental configuration files 64 may include but are notlimited to: a subscription file; a messaging file; a channels file; anadd to library file; a ratings file; a ratings mapping file; and a radioPC file.

The Subscriptioninfo.xml File

The subscriptioninfo.xml file may be provided 202 to personal mediadevice 38 and may define the basic details of the user's account status,including the user name, the type of account and the time remainingbefore the subscription licenses expires.

An example of the subscriptioninfo.xml file is as follows:

<?xml version=“1.0” encoding=“UTF-8”?> <xsl:stylesheetxmlns:xsl=“http://www.w3.org/TR/WD-xsl”>  <xsl:template>  <!--SubscriptionInfo Block (Read/Write)-->   <SubscriptionInfo>   <!--Rhapsody User ID GUID-->    <UserIDGUID/>    <!--User ID Text-->   <UserID/>    <!--Boolean - TRUE- Trial Active, FALSE, regularsubscription-->    <TrialActive/>    <!--ToGo, Unlimited, Channels-->   <AccountType/>    <!-Duration of DRM license, use TimeOfLicense andDuration to    find expire-->    <LicenseDuration/>    <!--Time whenlast licensed as an absolute date-->    <TimeOfLicense/>    <!-Officialname of service for use in UI ex. Rhapsody or Best Buy    Digital MusicStore-->    <ServiceName/>   </SubscriptionInfo>  </xsl:template></xsl:stylesheet>

For illustrative purposes, the subscriptioninfo.xml file may define oneor more of the following functionalities:

-   -   If the TimeOfLicense, UserIDGUID and UserID fields are missing        or empty then the device is not yet registered to any user.    -   The TimeOfLicense and LicenseDuration fields return information        that may indicate when the device was last registered and when        that registration expires. The date/time values may be denoted        in seconds from a standard time value.

The Messaging.xml File

The messaging.xml file may be provided 202 to personal media device 38and may allow media distribution system 16 and/or client-side mediamanager 46 to provide startup and shutdown messaging alerts for personalmedia device 38. Media distribution system 16 and/or client-side mediamanager 46 may specify whether the messaging alert is enabled/disabledand the message duration, priority and text for both the startup andshutdown messages. Additionally, a service logo may be displayed uponpersonal media device 38 starting up.

An example of the messaging.xml file is as follows:

<?xml version=“1.0” encoding=“UTF-8”?> <xsl:stylesheetxmlns:xsl=“http://www.w3.org/TR/WD-xsl”>  <xsl:template>  <!--DeviceMessaging(R)-->   <Messaging>   <!--Startup Messages-->  <StartupMessage>    <MessageEnable/>    <MessageText/>   <MessageDuration/>    <MessageAttributes/>   </StartupMessage>  <!--Shutdown Messages to the user-->   <ShutdownMessage>   <MessageEnable/>    <MessageText/>    <MessageDuration/>   <MessageAttributes/>   </ShutdownMessage>  <!--Service SpecificSplash screen-->    <ServiceLogo>   <LogoEnable/>   <LogoDuration/>  <!--path or object id of image file to use as logo screen-->  <LogoPath/>   </ServiceLogo>   </Messaging>  </xsl:template></xsl:stylesheet>

The Channels.xml File

The channels.xml file may be provided 202 to personal media device 38 ifmain configuration file 62 indicates that personal media device 38supports channels.

As discussed above, a channel may be considered an “endless” playlistthat is programmed by media distribution system 16 and/or client-sidemedia manager 46. The channels.xml file may provide a pointer to thelast track rendered within the channel playlist so that playback mayresume at the place where rendering stopped. If personal media device 38supports channels, personal media device 38 may provide a user interfacefor selecting a channel.

Whenever e.g., user 20 couples personal media device 38 to mediadistribution system 16 and/or client-side media manager 46, the channelson personal media device 38 may be refreshed. For example, any tracksthat have been rendered may be replaced with new tracks. However,unrendered tracks may be left on personal media device 38 for futurerendering. When media tracks for use within a channel are written topersonal media device 38, the tracks may be hidden and are typically notconsidered to be part of the music library of personal media device 12.

An example of the channels.xml file is as follows:

<?xml version=“1.0” encoding=“UTF-8”?> <xsl:stylesheetxmlns:xsl=“http://www.w3.org/TR/WD-xsl”>  <xsl:template>   <!--ChannelsBlock (Read/Write)-->   <Channels>    <!--Channel entry-->    <Channel>   <Restricted/>    <ChannelID/>    <ChannelType/>    <PlaylistPath/>    <PlaylistPUOID/>    <ChannelTitle/>    <ChannelDescription/>   <LastUpdated/>    <ChannelSize/>    </Channel>   </Channels></xsl:template> </xsl:stylesheet>

The AddToLibrary.dat File

The addtolibrary.dat file may be provided 202 to personal media device38 and may be read and cleared by media distribution system 16 and/orclient-side media manager 46 when personal media device 38 is coupled tomedia distribution system 16 and/or client-side media manager 46. Theaddtolibrary.dat file may include a list of track identifiers that user20 has added to their library while listening to the channels includedwithin personal media device 38. The track identifiers may be includedwithin the PlaysForSure metadata of the track to be added.

As discussed above and as is known in the art, channels are similar toradio stations on personal media device 38, which automatically updatewith new media content that replaces the media content that the useralready listened to. This automatic updating process may occur each timethat personal media device 38 is coupled with media distribution system16 and/or client-side media manager 46. In the event that a user (e.g.,user 20) likes a track that was included within a channel, user 20 mayadd that track to their library through e.g., one or more menus (notshown) displayable on display panel 116 and navigable by user 20.

Personal media device 38 may write, to the above-describedaddtolibrary.dat file, identifying information that defines the track tobe added to the library. As discussed above, MTP is a set of customextensions of the Picture Transfer Protocol (PTP) devised by Microsoft™that allows for the transfer of media data from various clientelectronic devices (e.g., personal media devices 36, 38, personaldigital assistant 40 and data-enabled cellular telephone 42) to personalcomputers.

MTP may use a plurality of object properties including (but not limitedto) the “SyncID” object property. The “SyncID” object property may beused by media distribution system 16 and personal media device 38 totransfer track-specific information between system 16 and device 38.Numerous pieces of information may be included within “SyncID”, examplesof which may include but are not limited to:

-   -   versionid: The “versionid” may define the version of media        distribution system 16. As discussed above, an example of media        distribution system 16 is the Rhapsody™ service offered by        RealNetworks, Inc. of Seattle, Wash. Accordingly, the        “versionid” may define the version of the Rhapsody™ service.    -   trackid: The “trackid” may define an ID for the track that is        understandable by media distribution system 16. As discussed        above, an example of media distribution system 16 is the        Rhapsody™ service offered by RealNetworks, Inc. of Seattle,        Wash. Accordingly, the “trackid” may be a Rhapsody Track ID that        defines a particular track available through the Rhapsody™        service.    -   artistid: The “artistid” may define an ID for the artist that is        understandable by media distribution system 16. The “artistid”        may be optional, as some artists may not have an artist id        within media distribution system 16.    -   albumid: The “albumid” may define an ID for the album that is        understandable by media distribution system 16.    -   albumartistid: The “albumartistid” may define the an ID for the        album artist that is understandable by media distribution system        16. If an artist does not have an “artistid”, the artist may not        have an “albumartistid”.    -   genreid: The “genreid” may define an ID for the genre that is        understandable by media distribution system 16.

An example of “SyncID” is as follows:

rhap_ver=4.0|trackid=7307228|artistid=182811|albumid=1032148|       albumartistid=182811|genreid=2102

When a track is transferred to personal media device 38, device 38 mayprocess the “SyncID” to extract 206 the above-described versionid,trackid, artistid, albumid, albumartistid, and genreid from the “SyncID”and store 208 them within the device database (not shown) includedwithin personal media device 38. The device database (not shown) may bestored on storage device 66.

Once extracted, one or more of these various IDs (e.g., versionid,trackid, artistid, albumid, albumartistid, and genreid) may be includedwithin any of supplemental configuration files 64. For example, when auser is listening to a channel track and adds that track to theirlibrary, the pertinent ID information (e.g., trackid, artistid, albumid)may be retrieved from the device database (not shown) included withinpersonal media device 38 and the addtolibrary.dat file may be modifiedto include this information. When personal media device 38 subsequentlyreconnects to media distribution system 16, media distribution system 16and/or client-side media manager 46 may obtain the pertinent IDinformation (e.g., trackid, artistid, albumid) from the addtolibrary.datfile so that the system database (not shown) of media distributionsystem 16 may be updated to reflect the changes made to the user'slibrary.

The Ratings.dat File

The ratings.dat file may be provided 202 to personal media device 38 andmay be read and cleared by media distribution system 16 and/orclient-side media manager 46 when personal media device 38 is coupled tomedia distribution system 16 and/or client-side media manager 46. Theratings.dat file may include a list of track identifiers for the tracksthat user 20 has rated on personal media device 38 while uncoupled frommedia distribution system 16 and/or client-side media manager 46. Asdiscussed above, the track identifiers may be included within thePlaysForSure metadata of the track to be added.

The RadioPC.txt File

The radiopc.txt file may be provided 202 to personal media device 38 andmay be read and cleared by media distribution system 16 and/orclient-side media manager 46 when personal media device 38 is coupled tomedia distribution system 16 and/or client-side media manager 46. Theradiope.txt file may define the following:

-   -   A channel_id value for each channel.    -   A station_type value for each channel.    -   A tracks_played value may count how many tracks from a given        channel have been rendered. This tracks_played value may be used        by media distribution system 16 and/or client-side media manager        46 to intelligently update a channel's content when the device        is coupled to media distribution system 16 and/or client-side        media manager 46.    -   A track_index value may: (a) mark the position within a channel        where the device should begin rendering the next track; and (b)        provide media distribution system 16 and/or client-side media        manager 46 with information to intelligently update a channel's        content.    -   A channel_looped value may be set to “1” when the last track in        the corresponding channel has been played/skipped. This value        may be used by media distribution system 16 and/or client-side        media manager 46 to update the media tracks in a given channel.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made. Accordingly, otherimplementations are within the scope of the following claims.

1. A method comprising: obtaining a main configuration file from aclient electronic device upon the client electronic device being coupledto at least a portion of a media distribution system, the mainconfiguration file defining one or more enhanced functionalities of theclient electronic device; wherein the client electronic device iscoupled to the at least a portion of the media distribution system usinga binary transfer protocol configured to transfer media data from the atleast a portion of a media distribution system to the client electronicdevice.
 2. The method of claim 1 further comprising: providing one ormore supplemental configuration files to the client electronic device,wherein the one or more supplemental configuration files are chosen fromthe group consisting of: a subscription file; a messaging file; achannels file; an add to library file; a ratings file; a ratings mappingfile; and a radio PC file.
 3. The method of claim 2 wherein at least oneof the main configuration file and the one or more supplementalconfiguration files is an XML configuration file.
 4. The method of claim1 wherein the client electronic device is a MTP-enabled clientelectronic device.
 5. The method of claim 4 wherein the MTP-enabledclient electronic device is a PlaysForSure client electronic device. 6.The method of claim 1 wherein the at least a portion of the mediadistribution system includes a client-side media manager.
 7. The methodof claim 6 wherein the client-side media manager is configured tointerface with a server-side media distribution system.
 8. The method ofclaim 1 wherein the at least a portion of the media distribution systemincludes a server-side media distribution system.
 9. The method of claim1 wherein the client electronic device is configured to bewirelessly-coupled to the at least a portion of the media distributionsystem.
 10. The method of claim 1 wherein the client electronic deviceis configured to be hardwire-coupled to the at least a portion of themedia distribution system.
 11. The method of claim 1 further comprising:processing a SyncID, transferable using the binary transfer protocol, toextract one or more of a versionid, a trackid, an artistid, an albumid,an albumartistid, and a genreid; and storing one or more of theversionid, the trackid, the artistid, the albumid, the albumartistid andthe genreid within a device database included within the clientelectronic device.
 12. A computer program product residing on a computerreadable medium having a plurality of instructions stored thereon which,when executed by a processor, cause the processor to perform operationscomprising: obtaining a main configuration file from a client electronicdevice upon the client electronic device being coupled to at least aportion of a media distribution system, the main configuration filedefining one or more enhanced functionalities of the client electronicdevice; wherein the client electronic device is coupled to the at leasta portion of the media distribution system using a binary transferprotocol configured to transfer media data from the at least a portionof a media distribution system to a client electronic device.
 13. Thecomputer program product of claim 12 further comprising instructionsfor: providing one or more supplemental configuration files to theclient electronic device, wherein the one or more supplementalconfiguration files are chosen from the group consisting of: asubscription file; a messaging file; a channels file; an add to libraryfile; a ratings file; a ratings mapping file; and a radio PC file. 14.The computer program product of claim 13 wherein At least one of themain configuration file and the one or more supplemental configurationfiles is an XML configuration file.
 15. The computer program product ofclaim 12 wherein the client electronic device is a MTP-enabled clientelectronic device.
 16. The computer program product of claim 15 whereinthe MTP-enabled client electronic device is a PlaysForSure clientelectronic device.
 17. The computer program product of claim 12 whereinthe at least a portion of the media distribution system includes aclient-side media manager.
 18. The computer program product of claim 17wherein the client-side media manager is configured to interface with aserver-side media distribution system.
 19. The computer program productof claim 12 wherein the at least a portion of the media distributionsystem includes a server-side media distribution system.
 20. Thecomputer program product of claim 12 wherein the client electronicdevice is configured to be wirelessly-coupled to the at least a portionof the media distribution system.
 21. The computer program product ofclaim 12 wherein the client electronic device is configured to behardwire-coupled to the at least a portion of the media distributionsystem.
 22. The computer program product of claim 12 further comprisinginstructions for: processing a SyncID, transferable using the binarytransfer protocol, to extract one or more of a versionid, a trackid, anartistid, an albumid, an albumartistid, and a genreid; and storing oneor more of the versionid, the trackid, the artistid, the albumid, thealbumartistid and the genreid within a device database included withinthe client electronic device.